|
〕 | owner = RAML Workgroup | standard = | url = }} RESTful API Modeling Language (RAML) is a YAML-based language for describing RESTful APIs.〔(【引用サイトリンク】title=RAML 0.8 )〕 It provides all the information necessary to describe RESTful or practically-RESTful APIs. Although designed with RESTful APIs in mind, RAML is capable of describing APIs that do not obey all constraints of REST (hence the description "practically-RESTful"). It encourages reuse, enables discovery and pattern-sharing, and aims for merit-based emergence of best practices.〔(【引用サイトリンク】title=RAML - RESTful API Modeling Language )〕 ==History== RAML was first proposed in 2013. The initial RAML specification was authored by Uri Sarid, Emiliano Lesende, Santiago Vacas, and Damian Martinez. Development is managed by the RAML Workgroup. The current workgroup signatories include technology leaders from MuleSoft Inc. (Uri Sarid), AngularJS (Misko Hevery, Project Founder), Intuit Inc. (Ivan Lazarov, Chief Enterprise Architect), Box Inc. (Peter Rexer, Senior Platform Product Manager), PayPal Inc. (Jason Harmon, Head of API Design), Programmable Web & API Web Science (John Musser, Founder), Kin Lane (Presidential Innovation Fellow, Department of Veteran Affairs), SOA Software (Tony Gullotta, Director of Technology), and Cisco (Samar Choudary, Lead Architect, Application Integration Service Group). RAML is a trademark of CR7 The current version of RAML is not restricted to strictly RESTful APIs because it would have not applied to almost any existing APIs and not been feasible for most API initiatives to adopt today, so RAML is starting with the basics of RESTful APIs—resources, methods, parameters, and bodies that need not be hypermedia with plans to evolve from there While RAML could end up being just a proprietary vendor language there are a number of reasons why this language is interesting to the broader API community:〔(【引用サイトリンク】title=Why RAML is More than Another Proprietary Specification )〕 * RAML has been open-sourced along with tools and parsers for common languages. The development of RAML will be overseen by a steering committee of API and UX practitioners and there is an emerging ecosystem of third-party tools being developed around RAML〔(【引用サイトリンク】title=API Design Tooling From RAML )〕 * Mulesoft originally started with Swagger but realised that standard was best suited to documenting an existing API, not for designing an API from scratch. RAML evolved out of the need to support up-front API design in a succinct, human-centric language〔(【引用サイトリンク】title=Anypoint for APIs: An Interview with Uri Sarid )〕 * API descriptions are often verbose and repetitive which can hinder their structure, understanding and consumption. RAML has introduced language features that support structured files, inheritance and that address cross-cutting concerns〔(【引用サイトリンク】title=An Example of API Design using RAML )〕 YAML was chosen as the baseline syntax for RAML because: * YAML is a very well known superset of JSON * YAML is optimized for human readability * YAML reveals hierarchies clearly and cleanly * YAML minimizes the need for curly brackets, quotes, and other "cruft" * YAML allows for internal references to minimize repetition and maximize succinctness * YAML has a very broad base of well known and understood tools 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「RAML (software)」の詳細全文を読む スポンサード リンク
|